Conversation
blakerouse
left a comment
There was a problem hiding this comment.
Can you provide a little more context on what this is doing? I don't fully understand.
Sure thing. When I refactored the updatecli pipelines in #5367 I changed the hardcoded values for the values in Unfortunately, I didn't test whether GitHub workflow changes worked as planned. In other words, I introduced a regression when I refactored the updatecli pipelines to be able to use the updatecli policies and reuse some of those variables between the different tupdatecli pipelines. |
blakerouse
left a comment
There was a problem hiding this comment.
Thanks for the details. Makes sense now.
|
/test |
|





What does this PR do?
Use the scm values file to be able to know what's the GH repository where those changes should be applied.
Why is it important?
Keep the automation doing what it was aimed to do :)
#5367 introduced a regression when replaced the hardcoded values for the values in a file. It's required to pass the new values file to the updatecli apply command, that's something I missed to do it.
Test
I ran the below command
Checklist
./changelog/fragmentsusing the changelog toolDisruptive User Impact
How to test this PR locally
Related issues
Questions to ask yourself